System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network

ABSTRACT

The disclosure includes systems and methods of use of an HVAC graphical interface dashboard. In various embodiments the dashboard includes a weather tab, wherein invoking the weather tab advances to a weather screen. The dashboard also includes an indoor humidity tab, wherein invoking the indoor humidity tab advances to a humidity screen which displays at least a current indoor humidity. The dashboard further includes an alerts tab, wherein invoking the alerts tab advances to an alerts screen. The dashboard still further includes a help tab, wherein invoking the help tab advances to a help screen that provides context sensitive help that presents at least one dialog box related to a function of a current screen. A programs tab and a home tab are also provided, and a subnet controller informs said dashboard to display a specific screen and instructs it how to fill in data.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Ser.No. 61/167,135, filed by Grohman, et al., on Apr. 6, 2009, entitled“Comprehensive HVAC Control System”, and is a continuation-in-partapplication of application Ser. No. 12/258,659, filed by Grohman on Oct.27, 2008, entitled “Apparatus and Method for Controlling anEnvironmental Conditioning Unit,” both of which are commonly assignedwith this application and incorporated herein by reference. Thisapplication is also related to the following U.S. patent applications,which are filed on even date herewith, commonly assigned with thisapplication and incorporated herein by reference:

Serial No. Inventors Title 12/603,464 Grohman, “Alarm and DiagnosticsSystem and et al. Method for a Distributed-Architecture Heating,Ventilation and Air Conditioning Network” 12/603,534 Wallaert, “FlushWall Mount Controller and In-Set et al. Mounting Plate for a Heating,Ventilation and Air Conditioning System” 12/603,449 Thorson, “System andMethod of Use for a User et al. Interface Dashboard of a Heating,Ventilation and Air Conditioning Network” 12/603,382 Grohman “DeviceAbstraction System and Method for a Distributed-Architecture Heating,Ventilation and Air Conditioning Network” 12/603,526 Grohman,“Communication Protocol System and et al. Method for aDistributed-Architecture Heating, Ventilation and Air ConditioningNetwork” 12/603,527 Hadzidedic “Memory Recovery Scheme and DataStructure in a Heating, Ventilation and Air Conditioning Network”12/603,490 Grohman “System Recovery in a Heating, Ventilation and AirConditioning Network” 12/603,473 Grohman, “System and Method for Zoninga et al. Distributed-Architecture Heating, Ventilation and AirConditioning Network” 12/603,525 Grohman, “Method of ControllingEquipment in a et al. Heating, Ventilation and Air Conditioning Network”12/603,512 Grohman, “Programming and Configuration in a et al. Heating,Ventilation and Air Conditioning Network” 12/603,431 Mirza, “GeneralControl Techniques in a et al. Heating, Ventilation and Air ConditioningNetwork”

TECHNICAL FIELD

This application is directed, in general, to HVAC systems and, morespecifically, to a user interface dashboard and installer interfacedashboard for a distributed-architecture heating, ventilation and airconditioning (HVAC) network, and methods of use thereof.

BACKGROUND

Climate control systems, also referred to as HVAC systems (the two termswill be used herein interchangeably), are employed to regulate thetemperature, humidity and air quality of premises, such as a residence,office, store, warehouse, vehicle, trailer, or commercial orentertainment venue. The most basic climate control systems either moveair (typically by means of an air handler, or more colloquially, a fanor blower), heat air (typically by means of a furnace) or cool air(typically by means of a compressor-driven refrigerant loop). Athermostat is typically included in the climate control systems toprovide some level of automatic temperature control. In its simplestform, a thermostat turns the climate control system on or off as afunction of a detected temperature. In a more complex form, a thermostatmay take other factors, such as humidity or time, into consideration.Still, however, the operation of a thermostat remains turning theclimate control system on or off in an attempt to maintain thetemperature of the premises as close as possible to a desired setpointtemperature. Climate control systems as described above have been inwide use since the middle of the twentieth century.

SUMMARY

In a first aspect the disclosure provides an HVAC graphical interfacedashboard. In an embodiment the dashboard includes a weather tab,wherein invoking the weather tab advances to a weather screen. Thedashboard also includes an indoor humidity tab, wherein invoking theindoor humidity tab advances to a humidity screen which displays atleast a current indoor humidity. The dashboard further includes analerts tab, wherein invoking the alerts tab advances to an alertsscreen. The dashboard also further includes a help tab, wherein invokingthe help tab advances to a help screen that provides context sensitivehelp that presents at least one dialog box related to a function of acurrent screen. The dashboard yet also further includes an indoorsettings tab, wherein invoking the indoor settings tab advances to anindoor settings screen which includes a current indoor temperature. Thedashboard still further includes a programs tab, wherein invoking theprograms tab advances to a programs screen wherein the programs screenincludes a display of a plurality of pre-populated program schedulesettings. The dashboard yet still further includes a home tab, whereininvoking the home tab advances to a home screen which provides a summaryof indoor conditions.

In another aspect the disclosure provides a method for operating an HVACinterface having a plurality of tabs. In an embodiment the methodincludes: providing a weather tab, wherein invoking the weather tabadvances to a weather screen. The method also includes providing anindoor humidity tab, wherein invoking the indoor humidity tab advancesto a humidity screen which displays at least a current indoor humidity.The method further includes providing an alerts tab, wherein invokingthe alerts tab advances to an alerts screen. The method yet furtherincludes providing a help tab, wherein invoking the help tab advances toa help screen that provides context sensitive help that presents atleast one dialog box related to a function of a current screen. Themethod yet still further includes providing an indoor settings tab,wherein invoking the indoor settings tab advances to an indoor settingsscreen which includes a current indoor temperature. The method also yetfurther includes providing a programs tab, wherein invoking the programstab advances to a programs screen wherein the programs screen includes adisplay of a plurality of pre-populated program settings. The methodalso includes providing a home tab, wherein invoking the home tabadvances to a home screen which provides a summary of indoor conditions.The method also yet still further includes invoking one of the screens.

A third aspect provides an HVAC system including a graphical interfacedashboard and at least one coupled device. In an embodiment thedashboard includes a weather tab, wherein invoking the weather tabadvances to a weather screen. The dashboard also includes an indoorhumidity tab, wherein invoking the indoor humidity tab advances to ahumidity screen which displays at least a current indoor humidity. Thedashboard further includes an alerts tab, wherein invoking the alertstab advances to an alerts screen. The dashboard further includes a helptab, wherein invoking the help tab advances to a help screen thatprovides context sensitive help that presents at least one dialog boxrelated to a function of a current screen. The dashboard yet alsofurther includes an indoor settings tab, wherein invoking the indoorsettings tab advances to an indoor settings screen which includes acurrent indoor temperature. The dashboard still further includes aprograms tab, wherein invoking the programs tab advances to a programsscreen wherein the programs screen includes a display of a plurality ofpre-populated program settings. The dashboard yet still further includesa home tab, wherein invoking the home tab advances to a home screenwhich provides a summary of indoor conditions. The second aspect furtherincludes at least one coupled device selected from the group including:a) an air handler, b) a furnace, c) an evaporator coil, d) a condensercoil and e) a compressor, wherein at least one coupled device isviewable from at least one of the tabs.

BRIEF DESCRIPTION

Reference is now made to the following descriptions taken in conjunctionwith the accompanying drawings, in which:

FIG. 1 is a high-level block diagram of an HVAC system within which adevice abstraction system and method may be contained or carried out;

FIG. 2 is a high-level block diagram of one embodiment of an HVAC dataprocessing and communication network 200;

FIG. 3A is a diagram of a series of steps in an event sequence thatdepicts a device commissioning in an HVAC network having an activesubnet controller;

FIG. 3B is a diagram of a series of steps that occur in relation to acommissioning of a subnet including an addressable unit;

FIG. 3C is a diagram of the above series of steps of FIG. 3B to befollowed by a subnet controller to synchronize with a device of the HVACsystem;

FIG. 3D is a high-level block diagram of one embodiment of a dashboardof a user interface for an HVAC system having a plurality of tabs, eachtab configured to invoke one or more corresponding screens;

FIGS. 3E-1 and 3E-2 illustrate a table that discloses subject matter ofscreens correlated to tabs of FIG. 3D;

FIG. 4 is a high-level flow diagram of exemplary transitions, for both auser and an installer, between various screens corresponding to varioustabs of the dashboard of FIG. 3 and various screens of an interfacedashboard of FIGS. 7A and 7B, and an inter-relationship between FIG. 3Dand FIGS. 7A and 7B;

FIG. 5 is an exemplary flow diagram of the user interface screens ofFIG. 4, illustrated in more detail;

FIG. 5A illustrates one embodiment of exemplary screens that bold aselected item when that selected item is compared to other selecteditems in a list of a tab of the dashboard of FIG. 3D;

FIG. 5B illustrates, in one embodiment, a partial and complete lockingof a screen of the dashboard of FIG. 3D;

FIG. 5C illustrates, in one embodiment, an employment of icons forvarious devices instead of text entries of the dashboard of FIG. 3D;

FIGS. 5D-1 through 5D-4 illustrate an employment of an embodiment of amotion detector for use with the dashboard of FIG. 3;

FIG. 5E illustrates a selection in an exemplary screen of the dashboard350 of an item through an employment of a text item itself as a buttonto select the item to which the text item correlates;

FIG. 6A illustrates an exemplary employment of a humidity graphic to sethumidity and de-humidity setpoints of a humidity screen of the humiditytab of FIG. 3D;

FIGS. 6B-1-6B-4 illustrates an exemplary employment of screen selectablesettings for setting a humidity point in a humidity screen of FIG. 3Dthat is dependent upon equipment installed in the HVAC system of FIG. 1;

FIGS. 7Ai-7Aiv and 7Bi-7Biv illustrate an exemplary flow of varioustransitions of a help screen that arise as a result of a previous screenof FIG. 3D;

FIGS. 8A-8D illustrates exemplary screens of found equipment thatappears in an indoor settings tab of FIG. 3D as dependent upon equipmentbeing found in the HVAC system of FIG. 1;

FIG. 9A illustrates an exemplary plurality of program schedule setpointsdisplayed on one screen of a programs tab of FIG. 3;

FIGS. 9B-1 and 9B-2 illustrates an exemplary persistent color inversionfor a selected button until a next button press within the programsscreen of the programs tab of FIG. 3D;

FIG. 9C illustrates an exemplary deactivation of a time period withinthe programs screen of FIG. 3D;

FIGS. 9D-1 and 9D-2 illustrate embodiments of a virtual analog clock ina programs screen of FIG. 3D;

FIG. 9E illustrates one embodiment of a program screen that allows for areset of at least one value related to the dashboard of FIG. 3D;

FIG. 9F illustrates one embodiment of a slider for setting a comfortpoint for a programs screen of FIG. 3D;

FIGS. 9Fi and 9Fii illustrate exemplary flows of a transition of aprograms screen of the dashboard of FIG. 3D;

FIG. 10A illustrates an exemplary movement of a finger across a homescreen to allow access to either an installer or a zone screen for anembodiment of the dashboard of FIG. 3D;

FIG. 10B illustrates an exemplary invocation of a plurality of dashboardtabs from a home screen of FIG. 3D;

FIGS. 11A-1 and 11A-2 illustrate embodiments of an installer dashboardthat employs screens of FIG. 4;

FIG. 11B illustrates an exemplary display of minimum, maximum anddefault values for one embodiment of an installer screen of FIGS. 11A1and 11A2 for a device connected to the HVAC system of FIG. 1;

FIG. 11C illustrates an exemplary underlining of default value for oneembodiment of an installer screen of an installer screen of FIGS. 11A1and 11A2;

FIGS. 11D-1 and 11D-2 illustrates an exemplary moving a device icon foran item to be diagnosed to a right side of a diagnostic screen of anembodiment of the installer dashboard of an installer screen of FIGS.11A1 and 11A2;

FIG. 12 illustrates an exemplary method for providing an interface foran HVAC system of FIG. 1; and

FIGS. 13A and 13B illustrate a subnet controller teaching a userinterface how to interpret data on a network within bounds earlierdefined as a user interface screen.

DETAILED DESCRIPTION

As stated above, conventional climate control systems have been in wideuse since the middle of the twentieth century and have, to date,generally provided adequate temperature management. However, it has beenrealized that more sophisticated control and data acquisition andprocessing techniques may be developed and employed to improve theinstallation, operation and maintenance of climate control systems.

Described herein are various embodiments of an improved climate control,or HVAC, system in which at least multiple components thereofcommunicate with one another via a data bus. The communication allowsidentity, capability, status and operational data to be shared among thecomponents. In some embodiments, the communication also allows commandsto be given. As a result, the climate control system may be moreflexible in terms of the number of different premises in which it may beinstalled, may be easier for an installer to install and configure, maybe easier for a user to operate, may provide superior temperature and/orrelative humidity (RH) control, may be more energy efficient, may beeasier to diagnose and perhaps able to repair itself, may require fewer,simpler repairs and may have a longer service life.

FIG. 1 is a high-level block diagram of an HVAC system, generallydesignated 100. The HVAC system may be referred to herein simply as“system 100” for brevity. In one embodiment, the system 100 isconfigured to provide ventilation and therefore includes one or more airhandlers 110. In an alternative embodiment, the ventilation includes oneor more dampers 115 to control air flow through air ducts (not shown.)Such control may be used in various embodiments in which the system 100is a zoned system. In the context of a zoned system 100, the one or moredampers 115 may be referred to as zone controllers 115. In analternative embodiment, the system 100 is configured to provide heatingand, therefore, includes one or more furnaces 120, typically associatedwith the one or more air handlers 110. In an alternative embodiment, thesystem 100 is configured to provide cooling and, therefore, includes oneor more refrigerant evaporator coils 130, typically associated with theone or more air handlers 110. Such embodiment of the system 100 alsoincludes one or more compressors 140 and associated condenser coils 142,which are typically associated in one or more so-called “outdoor units”144. The one or more compressors 140 and associated condenser coils 142are typically connected to an associated evaporator coil 130 by arefrigerant line 146. In an alternative embodiment, the system 100 isconfigured to provide ventilation, heating and cooling, in which casethe one or more air handlers 110, furnaces 120 and evaporator coils 130are associated with one or more “indoor units” 148, e.g., basement orattic units.

For convenience in the following discussion, a demand unit 155,sometimes referred to as a unit 155, is representative of the variousunits exemplified by the air handler 110, furnace 120, and compressor140, and more generally includes an HVAC component that provides aservice in response to control by the control unit 150. The service maybe, e.g., heating, cooling, or air circulation. The demand unit 155 mayprovide more than one service, and if so, one service may be a primaryservice, and another service may be an ancillary service. For example,for a cooling unit that also circulates air, the primary service may becooling, and the ancillary service may be air circulation (e.g. by ablower).

The demand unit 155 may have a maximum service capacity associatedtherewith. For example, the furnace 120 may have a maximum heat output(often expressed in terms of British Thermal Units (BTU) or Joules), ora blower may have a maximum airflow capacity (often expressed in termsof cubic feet per minute (CFM) or cubic meters per minute (CMM)). Insome cases, the demand unit 155 may be configured to provide a primaryor ancillary service in staged portions. For example, blower may havetwo or more motor speeds, with a CFM value associated with each motorspeed.

One or more control units 150 control one or more of the one or more airhandlers 110, the one or more furnaces 120 and/or the one or morecompressors 140 to regulate the temperature of the premises, at leastapproximately. In various embodiments to be described, the one or moredisplays 170 provide additional functions such as operational,diagnostic and status message display and an attractive, visualinterface that allows an installer, user or repairman to perform actionswith respect to the system 100 more intuitively. Herein, the term“operator” will be used to refer collectively to any of the installer,the user and the repairman unless clarity is served by greaterspecificity.

One or more separate comfort sensors 160 may be associated with the oneor more control units 150 and may also optionally be associated with oneor more displays 170. The one or more comfort sensors 160 provideenvironmental data, e.g. temperature and/or humidity, to the one or morecontrol units 150. An individual comfort sensor 160 may be physicallylocated within a same enclosure or housing as the control unit 150. Insuch cases, the commonly housed comfort sensor 160 may be addressedindependently. However, the one or more comfort sensors 160 may belocated separately and physically remote from the one or more controlunits 150. Also, an individual control unit 150 may be physicallylocated within a same enclosure or housing as a display 170. In suchembodiments, the commonly housed control unit 150 and display 170 mayeach be addressed independently. However, one or more of the displays170 may be located within the system 100 separately from and/orphysically remote to the control units 150. The one or more displays 170may include a screen such as a liquid crystal display (not shown).

Although not shown in FIG. 1, the HVAC system 100 may include one ormore heat pumps in lieu of or in addition to the one or more furnaces120, and one or more compressors 140. One or more humidifiers ordehumidifiers may be employed to increase or decrease humidity. One ormore dampers may be used to modulate air flow through ducts (not shown).Air cleaners and lights may be used to reduce air pollution. Air qualitysensors may be used to determine overall air quality.

Finally, a data bus 180, which in the illustrated embodiment is a serialbus, couples the one or more air handlers 110, the one or more furnaces120, the one or more evaporator coils 130, the one or more condensercoils 142 and compressors 140, the one or more control units 150, theone or more remote comfort sensors 160 and the one or more displays 170such that data may be communicated therebetween or thereamong. As willbe understood, the data bus 180 may be advantageously employed to conveyone or more alarm messages or one or more diagnostic messages.

FIG. 2 is a high-level block diagram of one embodiment of an HVAC dataprocessing and communication network 200 that may be employed in theHVAC system 100 of FIG. 1. One or more air handler controllers (“AHCs”)210 may be associated with the one or more air handlers 110 of FIG. 1.One or more integrated furnace controllers (“IFCs”) 220 may beassociated with the one or more furnaces 120. One or more dampercontroller modules 215, also referred to herein as a zone controllermodule 215, may be associated with the one or more dampers 114 thatinterface the one or more dampers to the data bus 180. One or moreunitary controllers 225 may be associated with one or more evaporatorcoils 130 and one or more condenser coils 142 and compressors 140 ofFIG. 1. The network 200 includes an active subnet controller (“aSC”) 230a and an inactive subnet controller (“iSC”) 230 i. The aSC 230 a isresponsible for configuring and monitoring the system 100 and forimplementation of heating, cooling, air quality, ventilation or anyother functional algorithms therein. Two or more aSCs 230 a may also beemployed to divide the network 200 into subnetworks, or subnets,simplifying network configuration, communication and control. The iSC230 i is a subnet controller that does not actively control the network200. In some embodiments, the iSC 230 i listens to all messages passedover the data bus 180, and updates its internal memory to match that ofthe aSC 230 a. In this manner, the iSC 230 i may backup parametersstored by the aSC 230 a, and may be used as an active subnet controllerif the aSC 230 a malfunctions. Typically there is only one aSC 230 a ina subnet, but there may be multiple iSCs therein, or no iSC at all.Herein, where the distinction between an active or a passive SC is notgermane, the subnet controller is referred to generally as an SC 230.

A user interface (“UI”) 240 provides a means by which an operator maycommunicate with the remainder of the network 200. In an alternativeembodiment, a user interface/gateway (UI/G) 250 provides a means bywhich a remote operator or remote equipment may communicate with theremainder of the network 200. Such a remote operator or equipment isreferred to generally as a remote entity. A comfort sensor interface260, referred to herein after simply as a comfort sensor, may provide aninterface between the data bus 180 and each of the one or more comfortsensors 160.

Each of the components 210, 220, 225, 230 a, 230 i, 240, 250, 260 mayinclude a general interface device configured to interface to the databus 180, as described below. (For ease of description any of thenetworked components, e.g., the components 210, 220, 225, 230 a, 230 i,240, 250, 260, may be referred to generally herein as a device 290. Inother words, the device 290 of FIG. 2 is a proxy for any of a furnace, aheat pump, a subnet controller, etc, and that device's associatedinterface means.) The data bus 180 in some embodiments is implementedusing the Bosch CAN (Controller Area Network) specification, revision 2,and may be synonymously referred to herein as a residential serial bus(“RSBus”) 180. The data bus 180 provides communication between or amongthe aforementioned elements of the network 200. It should be understoodthat the use of the term “residential” is nonlimiting; the network 200may be employed in any premises whatsoever, fixed or mobile. In wirelessembodiments, the data bus 180 may be implemented, e.g., using Bluetooth™or a similar wireless standard.

Generally, the network 200 allows for the remote comfort sensors 160,the control unit 150, and user display 170 and/or remote user displays170 to operate independently as separate logical units, and can belocated in separate locations within the network 200. This is unlike theprior art, wherein these functionalities were required to be locatedwithin a single physical and logical structure.

Turning now to FIG. 3A, illustrated is a diagram of a commissioningprocess 300 of a series of steps that occur in relation to acommissioning of the demand unit 155. The commissioning process 300includes an enter state 301, a device commissioning state 303, and anexit state 305. The HVAC system 100 can be described as beingpartitioned into a plurality of subnets, each subnet controlled by itsown active subnet controller 230.

Device commissioning can generally be defined as setting operationalparameters for a device in the network of the HVAC system, including itsinstallation parameters. Generally, the commissioning process 300 isused by the subnet controller 230 when it is active to: a) set operating“Installer Parameters” for a networked device, such as air handlers 110,(henceforth to be referred to collectively, for the sake of convenience,as the demand unit 155, although other devices are also contemplated),b) to load UI/Gs 240, 250 with names and settings of “InstallerParameters and Features” of the demand units 155, c) to configurereplacement parts for the demand units 155, and d) to restore values of“Installer Parameters and Features” in the demand units 155 if those“Parameters and Features” were lost due to memory corruption or anyother event. Device commissioning is a process used in the HVAC system100, either in a “configuration” mode or in a “verification” mode.

In the “configuration” mode, the demand unit 155 shares its informationwith the active subnet controller 230 a in an anticipation of beingemployable in the HVAC system 100, and an appropriate subnet. Generally,the commissioning process 300 provides a convenient way to change orrestore functional parameters, both for the active subnet controller 230a and the demand unit 155.

In both the “verification” mode and the “configuration” mode, the demandunit 155 is checked for memory errors or other configuration orprogramming errors. There are differences in device 290 behavior betweenthe “configuration” mode and in the “verification” mode, to be detailedbelow.

The “subnet startup” mode programs the subnet controller 230 to beactive. The “subnet startup” mode enables subnet communications, (i.e.,communication within a subnet), and also deactivates a “link” sub-mode.A “link” mode may be generally defined as a mode that allows a number ofsubnets to work together on the same HVAC network 200, and that assignssubnet numbers for each subnet to allow this communication.

The “installer test” mode is employed when an installer installs andtests aspects and demand units 155 of the HVAC system 100. The “normaloperations” mode is an ongoing operation of devices 290 of the HVACsystem 100 in a normal use.

More specifically, the device commissioning process 300 can be employedwith: a) the “configuration” mode, which is invoked when transitioningto the commissioning state 303 from the “subnet startup mode” or“installer test” mode, or the “normal mode” (see below), or b) a“verification” mode. The “verification” mode is invoked whentransitioning to the commissioning state 303 from the “subnet startup”mode.

The following describes an illustrative embodiment of a using theprocess 300 to commission the demand unit 155, first for a “commission”mode, and then for a “verification” mode. The process of commissioningdiffers from a “subnet startup,” in that commissioning requires that thenetwork configuration, including configuration and activation of subnetcontrollers 230, has already been completed before the commissioningprocess 300 for the device 290 can start. Please note that there can bemore than one subnet controller 230 on a subnet, but only one subnetcontroller 230 a is active at any one time.

In one embodiment, in order to enter into a state 320 of a state machine310 (described in detail below with respect to FIG. 3B) in the“configuration” mode, the unit 155 receives either: a) an “aSC” (‘activesubnet controller’) Device Assignment message”, having “Assigned State”bits set to “Commissioning”; or b) a receipt of an “aSC Change State”message, with “New aSC State” bits set to “Commissioning,” from theactive subnet controller 230. For both “configuration” and“verification” modes, an “aSC Device Assignment” message can begenerally regarded as a message that assigns the unit 155 to aparticular active subnet controller 230 a. For both “configuration” and“verification” modes, an “aSC Change State” message can be generallyregarded as a message that starts and ends employment of thecommissioning process 300 for the devices 290.

In one embodiment, in the state 320 in the configuration mode, all units155 respond to the “aSC Device Assignment” message with their respective“Device Status” messages, indicating that the units 155 are now in thecommissioning process 300 due to their response to this previousmessage. For both “configuration” and “verification” modes, the “DeviceStatus” message can be generally defined as a message that informs theactive subnet controller 230 a of what actions are being taken by theunit 155 at a given time.

However, alternatively in other embodiments, in the state 320 in the“configuration” mode, if the units 155 are instead busy, as indicated by“aSC Acknowledge” bits of the “Device Status” message sent to the activesubnet controller 230 a set as a “Control Busy,” the active subnetcontroller 230 a waits for the busy units 155 to clear their “aSCAcknowledge” bits before proceeding with further elements of theCommissioning process 300. The units 155 then resend their “DeviceStatus” messages as soon as they are no longer busy.

From this point on, all units 155 send their “Device Status” messagesperiodically and on any status change, both during and after thecommissioning process 300. If the unit 155 does not clear its “aSCAcknowledge” bits within a minute, the active subnet controller 230 asends an “Unresponsive Device2” alarm for each such unit 155. If in“configuration” mode, the active subnet controller 230 a remains in thewaiting mode indefinitely, until the unit 155 responds correctly, or thesubnet is reset manually or after a timeout is reached. In“verification” mode the active subnet controller 230 a proceeds furtherto exit the state.

In the “configuration” mode, each unit 155 remembers all of its optionalsensors that are currently attached to it. Furthermore, each unit 155may store a local copy in its non-volatile memory (“NVM”) of any otherunit features that it is dependent on. A unit 155 feature can begenerally defined as any datum that is fixed and cannot be changed bythe installer, serviceman or the home owner. Changing of a “Feature”value normally involves reprogramming of the unit's 155 firmware.

In at least some embodiments, a feature is something that is a fixedvalue, that is hard-wired into a device. In other words, no installer orhome owner can change it. Features are programmed into the unit 155during a manufacturing or an assembly process. Features can be recoveredin a home, during a Data non-volatile memory (“NVM”) recovery substateof Commissioning state only—the recovery substate happens automaticallyand without installer or user intervention. In a further embodiment,parameters can be changed by the installers only. In a yet furtherembodiment, the network 200 of the HVAC system 100 employs“variables”—those can be changed by the installers and also the homeowners.

In some embodiments, a “Parameter List” is normally a Feature thatcontains a special list of specific parameters included in the unit 155.Parameter values can be changed, and their state can be changed also(from enabled to disabled and vice-versa), but their presence is setonce and for all in a given firmware version. Therefore, a list ofParameters (not their values) is also fixed, and is thus treated as a“Feature.”

However, although elements of the “configuration” mode commissioning and“verification” mode commissioning are similar, when the active subnetcontroller 230 is in “verification” mode instead of in “configuration”mode, the active subnet controller 230 a can exit commissioning process300 regardless of the value of the alarms of the units 155. However,alternatively, if the active subnet controller 230 a is in“configuration” mode, the active subnet controller 230 a will not exitfrom its commissioning process 300 for as long as at least one unit's155 “aSC Acknowledge” flags are set to “Control Busy.” In one embodimentof the “verification” mode, the active subnet controller 230 a timeoutsthe installation and resets the subnet to default parameters.

In the “verification” mode, assuming the unit 155 operates with anon-corrupted (original or restored copy) NVM, each unit 155 checks anyof its attached sensors to see if they match with the parameters thatwere present in a most recent configuration of the unit 155. In someembodiments, alarms are generated by the unit 155 for missing ormalfunctioning sensors as soon as the faulty condition is detected, tobe employed by the user interfaces and gateways present on the subnet tonotify the installer or homeowner of the encountered problem. Theunexpected absence of certain sensors may inhibit the operation of theunit 155 or the subnet. This is normally manifested by the signaling ofthe appropriate Service Bits in the Device Status message used by theactive subnet controller 230 a, to determine the operational viabilityor health of the subnet's systems.

In some embodiments, the device commissioning process 300 (via the statemachine 310) then transitions into a link-mode startup state 330 (FIG.3B), and then ends, upon either: a) the last unit 155 receiving all ofunit 155 parameters that it is dependent on, when in “verification”mode; or b) upon a request by a user, when in “configuration” mode. Theactive subnet controller 230 then proceeds to ensure that no subnet unit155 has its “aSC Acknowledge” flag set to a “Control Busy” state. The“aSC Acknowledge” flag not being set indicates that all of anon-volatile memory of a given unit 155 had been written to with thenecessary parameters. If no “Control Busy” state is detected, the activesubnet controller 230 a then issues the “aSC Change State” message,which forces the unit 155 from a commissioning state to anon-commissioning state, in either a “configuration” or a “verification”mode.

In some embodiments, when the unit 155 in the process 300 fails its NVMdata integrity check in an “NVM Check State,” and the active subnetcontroller is unable to perform NVM Recovery, the unit 155 insteademploys its default data stored in its non-volatile (Flash) memoryand/or uses default calculations to initialize the data dependent onother devices in the system. The other device data to be used forcommissioning could have been obtained in either the “verification” or“configuration” mode. For data or other parameters that were nottransferred or generated as part of that session of the commissioningprocess 300, default values are used.

In one embodiment, upon a detection of a system configuration error,such as a missing device whose features or parameters the unit 155depends upon, it uses the locally stored copy of the other device'sfeatures that it depends upon, and ignores any potential feature valueconflicts. In another embodiment, the unit 155 uses the locally storedcopy of other parameters of the unit 155 that it depends on and ignoresany potential dependent parameter value conflicts. In other words, theunit 155 employs a first installed parameter as a template for a secondinstalled parameter on a second device. In a third embodiment, the unit155 will change its parameter or feature values only if explicitlyinstructed by the active subnet controller 230 or the UI/G 240, 250.

Turning now to FIG. 3B, illustrated is the HVAC device state machine 310illustrated for a subnet, including the unit 155, in more detail. Solidlines indicate normal state transitions when the subnet is transitioningfrom one state to another state, dashed lines indicate a subroutine calland red lines, alternating dotted and dashed lines indicate unexpectedyet valid transitions. All states other than a state 326 representdevice states, and the state 326 represents a message handling routine.

As is illustrated in the present embodiment, a reset state 312 of asubnet advances to a NVR CRC check 316 for a given device (such as unit155). If the device fails the test, the device advances to a device harddisable 314. If the device passes, however, then in the subnet startupstate 320, various features and parameters of the unit 155 are sharedwith the subnet. Then, in substate 324, device commissioning asdescribed in FIG. 3A occurs. This then leads to an installer testsub-mode 328. This, in turn, then leads to the link mode start-up 330,as described above. Finally, then in a step 334, normal system operationoccurs, although the system can reset to state 312 or have errormessages in the state 326.

In a further embodiment, during the NVM CRC check 316, the state machine310 can advance to a NVM programming state 318. This can occur due tosuch factors as a failure of a non-volatile memory, or an initialprogramming of the NVM. In a yet further embodiment, each of these units155 is programmed to deal with one form of a diagnostic messageregarding system errors in the state 326, and from there to testing thedevice 290 itself in an OEM test mode 332.

Turning now to FIG. 3C, illustrated is a state flow diagram 340 for theactive subnet controller 230 a in relation to the unit 155. Generally,it is the responsibility of the active subnet controller 230 a toimplement proper state transitions. The other units 155 follow theexplicit direction of the aSC 230 a for all valid transactions. Thesestate diagrams are included to help ensure that a state of the unit 155is the same as the subnet controller. The aSC 230 a is responsible fordevice synchronization. If the unit 155 is detected out of synch withthe rest of the system, the aSC 230 a, in some embodiments, immediatelytries to bring the unit 155 to the current system state, if possible.

If an addressable unit 155 is detected in subnet startup 344, the activesubnet controller 230 a applies asynchronous startup rules, whichgenerally pertain to how many parameters are to be passed between device290 and the active subnet controller 230.

If an addressable unit 155 is detected in commissioning 345, installertest 346, link mode 347 or normal operation 348 substates, the unit 155,in some embodiments, is brought to the current state via a resend of an“aSC Change State” message, which involves transitioning from a firstcurrent aSC state to a second current aSC state.

In some embodiments, if a unit 155 is detected in the OEM Test mode 332or a Soft Disabled state 322 (FIG. 3B), the unit 155 shall be reset bythe active subnet controller 230 a in the step 312. If a unit 155 isdetected in “Hard Disabled” or “NVM Programming” state, the activesubnet controller 230 a assumes that it is not available on the subnet.

In a further embodiment, inactive subnet controllers 230 i are requiredto keep the most up to date subnet and HVAC system configurationinformation. Inactive subnet controllers 230 i listen to all UI/G andaSC messages and continuously update their non-volatile memory toattempt to be as consistent as possible with the settings stored inactive subnet controller 230.

Aspects of Interface

FIG. 3D illustrates an exemplary HVAC user interface dashboard(“dashboard”) 350 to the user interface 240 to both read and program theactive subnet controllers 230 a, 230 i and other elements of the HVACnetwork 200 of the HVAC system 100. The dashboard 350 can be includedwithin the displays 170.

In the illustrated embodiment, the dashboard 350 includes a weather tab355, an indoor humidity tab 360, an alerts tab 365, a help tab 370, anindoor settings tab 375, a program schedule tab 380, sometimes referredto herein as a programs tab 380, a zones tab 385 and a home tab 390,each of which invokes its own corresponding user or installer interfacescreen or screens. There can be some redundancy of information orfunctionality between screens corresponding to the different tabs, buteach tab includes screens that contain at least some information orfunctionality that is not found in any other single tab. Furthermore,each tab can be either invoked by a user, such as through touching atab, or each tab can be invoked remotely, such as by an installer.

Reviewing FIG. 3D with aid of FIGS. 3E-1 and 3E-2, generally, pressingthe weather tab 355 advances a user to an exemplary weather screen. Theweather screen displays current outdoor weather if a current outdoortemperature and/or humidity is available.

Pressing the exemplary indoor humidity tab 360 advances a user to anindoor humidity screen. The humidity screen allows for the user tochange a system dehumidify mode. Dehumidify mode selections include:humidify, dehumidify, humidify and dehumidify and off. A user can cyclethrough these selections.

The exemplary indoor humidity screen allows a user to view both absoluteand relative humidity, and also to set “setpoints” for absolute andrelative humidity (i.e., points at which a humidifier or dehumidifier isturned on and off). In one embodiment, relative humidity (“RH”) canrange from 15% to 45% RH and can be either programmed or humidificationon demand.

Similarly, dehumidification can be from 40-40% RH and can be eitherprogrammed dehumidification or demand.

An indoor humidity screen also allows a user to view humidification anddehumidification comfort zones. In this context, a comfort zone can begenerally defined as a zone of a HVAC system that has separate setpointsfor temperature and humidity, etc.

Pressing the exemplary alerts tab 365 advances a user to an alertsscreen. The alerts screen allows a user to obtain dealer informationabout currently active alerts and set the dashboard 350 to remind a userlater for service alerts. In some embodiments, a select button of thealerts screen of the alerts tab 365 allows the user to obtain a dealer'scontact information. The select button allows the user to clear anactive alert (all service alerts and specified critical alerts, and alsoallows the user to clear an active alert (service or critical)). In someembodiments, when a “new service/critical alert” occurs or “remindlater” extension time expires, the dashboard 350 floods any currentscreen with an alert, in other words, the alert overlays any otherscreen.

An alarm message displays alerts visible to the user, whereas all alertsare visible to the installer. The installer can learn of these alertseither viewing the alerts tab 365 of the dashboard 350 in person orremotely through a message conveyed through the user interface/gateway250.

Pressing the exemplary help tab 370 advances a user to a help screen.The help screen can include context sensitive help, an option to clear ascreen and user system configuration. The context sensitive helppresents dialog boxes relating to a current screen's functions, and usersystem configurations can provide access to all user local settings(i.e., any setting that does not require an installer to make a change,but can instead by made by a user.)

In some embodiments, there can be a time-based notification ofconsumables in the help screen, either for the user or for an installer.These consumables can include, in some embodiments: media filters, UVbulbs and humidifier pads. All information concerning consumables can beaccessible by both the installer as well as the user via the helpscreen. In some embodiments, a user and installer can enable andmanually change the time settings for any timer of the HVAC system 100through the help screen. Similarly, a maintenance reminder can beaccessible by the installer, as well as the user, via the help screen.

Pressing the exemplary indoor settings tab 375 advances a user to anindoor settings screen. In one embodiment, the indoor settings screendisplay indoor temperature measurement and temperature settings. Theindoor settings also display the system mode settings and fan modesettings. In one embodiment, system mode selections include: heat, cool,heat and cool, off and emergency heat. Fan mode selections include:automatic, on and circulate. The dashboard 350 allows the user to changethe system mode and the fan mode through cycling through variouschoices.

In one embodiment, equipment employed within the system mode dictateswhich system modes (heat, cool, heat & cool, emergency heat) arevisible. For example, a “Heat & Cool” selection of the system mode isvisible only when both heating equipment and cooling equipment arepresent in the system. Typically, the system mode selection of “Off” isalways visible.

The indoor temperature settings screen also allows a user to changecurrent temperature setpoints, (i.e., points at which a heater or airconditioner is turned on and off) unless this would override aprogrammed setting, in which case, a hold occurs until an end of theprogrammed time occurs and the new setpoints become the operating valuesof the HVAC system 100.

The exemplary dashboard 350 also allows its system mode settings and fanmode settings to be obtained and changed via RSBus devices (e.g. UserInterface/Gateway 250 coupled to the bus 180) remotely. If the dashboard350 is requested, remotely or locally, to change the system mode to aninvalid setting, the system mode is not changed.

Furthermore, the indoor settings tab 375 allows for a user/installer toview all system information and comfort settings (i.e., temperature andhumidity) and allow editing of all current settings, as well as fan modesettings. The indoor settings tab 375 allows the fan mode (on, auto,circulate) to be obtained and changed via the RSBus (e.g., via bus 180and user interface/gateway 250.)

Pressing the exemplary programs tab 380 advances a user to a programsschedule screen. The programs schedule screen allows forviewing/editing/enabling future program schedule events (e.g.,temperature setpoints, system modes and fan modes) in the HVAC system100. The programs screen allows a programming of event times,temperature setpoints and fan mode for each pre-defined period. Aprogram schedule does not run when the system mode is set to “off.”

In one embodiment, the programs screen is seven-day programmable withthe ability to select multiple days for programming. In one embodiment,the programs screen is capable of programming up to four (4) events per24-hour period. In one embodiment, program schedules for temperaturesetpoints are programmed for a seven day schedule, up to four periodsper day and are stored in non-volatile memory. In one embodiment,program schedule events can be set in 15-minute increments of time. Thescheduled events execute in order based on time of day. In oneembodiment, the user interface 240 provides the capability toenable/disable any period of any given day by pressing the correspondingtime button for two seconds.

Generally, if a mode changes, such as a fan mode change, is made withinthe program schedule screen is made while a program schedule of theprograms tab 380 is actively executing, a program schedule “hold” modeis invoked until a next program schedule event, at which time the newsetpoint is acted upon. If a temperature setpoint change is made whilethe program schedule of the programs tab 380 is not active, thedashboard 350 updates the display with the new setpoint and acts uponthis new setpoint.

Generally, the exemplary dashboard 350 allows its programmed temperaturesetpoints (heat, cool) and modes to be obtained/changed via RSBusdevices (e.g. User Interface/Gateway 250 over the bus 180) remotely. Ifthe dashboard 350 is requested (remotely or locally) to change eithersetpoint, either temperature or humidity, to a setting beyond thesetpoint limits, the setpoint is not changed. If the dashboard 350 isrequested remotely or locally to change the fan mode or system mode toan invalid setting, the fan mode or system mode is not changed.

In some embodiments, the cooling setpoint is shown only when coolingequipment is present in the system. Likewise, the heating setpoint isshown only when heating equipment is present in the system. Thedashboard 350 may not allow two program scheduled events to begin at thesame time. In other words, there can be only one setpoint for either ahumidity or a temperature for a given time period—one for each.

In one embodiment, up and down arrows of a program screens of theprograms tab 380 allows the user to edit a selected box information. Asave button allows the user to save changes to the program schedule. Acancel button allows the user to quit the program schedule edit screenwithout saving changes. A back button returns the user to the programschedule day selection screen. (Not illustrated.)

In some embodiments, pressing the zones tab 385 advances a user to azone screen which, in one embodiment, is accessible only by an installerwith a proper key. Generally, the zone screen deals with informationthat is pertinent to programming HVAC equipment for variousenvironmental “zones” within the HVAC system (e.g., living room,bedroom, kitchen, etc.) The zone screen therefore advises the user tocontact the manufacture for more information regarding the zone screen.The zones tab 385 then either advances to a home screen of the programstab 380 or back to the overall user dashboard 350.

Generally, the home screen of the home tab 390 includes a summary ofindoor environmental conditions for a user. A home screen indicates astatus of the program schedule (ON, OFF). The home screen indicatestemperature control status (heating, cooling, off, waiting) as well ashumidity control (humidifying, dehumidifying, waiting) of the HVACsystem 100. In one embodiment, when a given system is set to “off,” only“system is off” is displayed in the home screen.

In some embodiments, the dashboard 350 returns to the home screen after30 seconds has elapsed since a last screen or tab press, including fromany other tab of the dashboard 350. In some embodiments, after a 30second period of inactivity, any changes made to a screen requiring anactive “set” or “save” button press are lost. The dashboard 350 insteadreturns to the home screen. In some further embodiments, after auser-selectable time period of inactivity, an initial screen press, evenupon a tab, causes only a backlight to activate with the home screen asthe initial screen shown. The home tab 390 can include a series ofscreens that are navigable from the home screen via an icon press.

Although not illustrated in FIG. 3D, an installer dashboard includinginstaller screens can also be accessed through the home screen by aninstaller with a proper key. Generally, the installer screens allow foran installation and configuration of various pieces of equipment in theHVAC system 100. The installer screens can also enable various defaultvalues as parameters of operation.

In some embodiments, when a button of a screen of the dashboard 350 isheld, the dashboard 350 initially displays an update to the value beingchanged at a rate of change of 0.5 seconds. After a button hold of 3seconds, the rate of change is increased to 0.25 seconds.

The user dashboard 350 can itself be a color and touch-screen. Thedashboard 350 can include a dynamic full color dot matrix LCD display. Atouch pad may be built into/over the dashboard 350. Typically, a maximumdelay between any key press and display feedback (indication by selectedbutton, screen change, etc.) is 0.2 seconds.

FIG. 4 illustrates a high-level flow diagram 400 of exemplarytransitions, for both user and installer, between user interface screenscorresponding to various tabs of the exemplary dashboard of FIG. 3D andvarious exemplary interface screens of an interface dashboard of FIGS.11A1 and 11A2.

The exemplary flow 400 has an installer screen flow 401 and a userscreen flow 451. The installer screen flow 401 of the dashboard 350provides access to all installer screens (including subnet start up,configuration, commissioning, installer tests, alerts and diagnostics).The screens of the user screen flow 451 are accessible through the tabs355-390 of FIG. 3D, with the exception of a new alert screen 452, whichthe dashboard 350 generates upon a new alert. In a further embodiment,the dashboard 350 allows each screen of the flow 400 to be invokedremotely by a user and/or installer via the User Interface/Gateway 250.

Upon power-up of the HVAC system 100, an installation tab 402 of theinstaller flow 401 appears. Unless an installer inputs a correct keycode within a given time period, the flow 400 transitions to a homescreen 450. However, if the installer inputs the correct key, aninstaller screen corresponding to the installer test tab 404 appears.The installer can then install and configure various devices in the HVACsystem 100. After installation, the installer flow 401 then advances tothe home screen 450.

In one embodiment, the installer flow 401 includes a series of screensthat are accessible from the home screen 450 via both a) an icon press;and then b) a correct entry of a correct key sequence. In oneembodiment, pressing a dealer logo, such as a “Lennox™” logo, on thehome screen 450 for 5 seconds allows an installer to execute systemstartup processes, as well as view/edit the alerts and diagnostics viathe installer configuration screens of the flow 401.

Generally, the home screen 450 provides a high level overview of thecurrent indoor conditions. The home screen 450, in some embodiments,displays the indoor temperature, indoor relative humidity status,outdoor temperature and system status (e.g. heating, cooling, off,humidifying, dehumidifying, etc.) of the HVAC system 100.

From the home screen 450, a warning screen 412 for an installer can begenerated by the dashboard 350. This warning screen 412 can be conveyedto an installer either directly when installer is present, or through aremote communication, such as over the bus 180 through gateway 250, andthen perhaps through the Internet to the installer. The warning screen412 generally states that there is a type of problem that should beaddressed by an installer, but may not give all details. Once thewarning screen 412 is acknowledged by an installer, an alerts tab 408has a screen that is the default screen for the dashboard 350.

From the warning screen 412, the installer can also advance to either adiagnostics screen of a diagnostics tab 406, a contextual help screen ofthe installer help tab 414, the installer screen of the installationsetup tab 402, or an installer screen of the installer test tab 404.

In some embodiments, for a user, from the home screen 450, the new alertscreen 452 can arise upon a first detection by the HVAC system 100 of analert. Similarly, the alerts tab 365 can be used to invoke and view analerts screen. In one embodiment, the alerts tab 365 can be used toaccess every other tab in the dashboard 350.

In the illustrated exemplary flow 400, the home screen 450 transitionsto either the alerts tab 365 if an active alert exists or the indoorsettings tab 375. From the indoor settings tab 375, all other user tabsare also accessible. These include the weather tab 355, the indoorhumidity tab 360, the alerts tab 365, the help tab 370, the programs tab380 and the zones tab 385. Please note that, in some embodiments, thezones tab 385 can transition to the home screen 450, and the zones ofthe zones tab 385 are typically set by an installer of the HVAC system100.

Regarding the alerts screen 452, in one embodiment, if the dashboard 350is displaying a popup alert at the time when another alert (to bedisplayed to the user) occurs, the dashboard 350 continues to displaythe current alert screen 452. When a current alert has been addressed,the dashboard then overwrites the screen with the newest alert. Ifmultiple popup alerts exist simultaneously, the dashboard 350 displayseach (in order of occurrence—timestamp) one-by-one after the previousnew alert is addressed. There is not a time-out for a new alert floodingthe screen. The new alert remains on the screen of the dashboard 350until addressed by the user/installer.

Turning briefly now to FIG. 5, illustrated are exemplary correspondingscreens of the tabs of FIGS. 3D and 4 illustrated in more detail. Theweather tab 355 can display weather info when available. The indoorhumidity tab 360 enables a user to set humidity modes and setpoints. Thealerts tab 365 can display alert info. The home screen 450 can interactwith the other illustrated tabs. The indoor settings tab 375 can setdisplay and set temperature conditions and settings (setpoints), overallsystem mode and fan mode. The programs tab 380 enables a user to programvarious times. The zones tab 385 forwards an admonition to the user torequest more information from the manufacturer, and then transfers backto the home screen 450.

Generally, FIGS. 5A through 5D-2, to be discussed below, illustrateaspects of the present disclosure that are applicable to at least some,and can be to all, of the user screens of FIG. 3D and FIG. 4.

Turning now to FIG. 5A, illustrated is an embodiment of the screen 500of the dashboard 350 that bolds a selected item 501, 503, 505, 507relative to other selected items in a list in the dashboard 350. Theuser can highlight a selected item in white; the other selected itemsare in grey.

Turning now to FIG. 5B, illustrated is an embodiment of an unlockedscreen mode 521, a partially locked screen mode 523, and a fully lockedscreen mode 525 of the dashboard 350. The partially locked screen mode523 places a lock-pad icon 526 over a text 524 that states “press formore,” and also deactivates all buttons except up-down arrows 529.Partially locked mode has a limited functionality.

In one embodiment, the fully locked mode 525 deactivates all buttons andremoves the up/down arrows from a screen. To unlock the partially lockedscreen mode 523 or the fully locked screen mode 525, a user presses andholds the lock-pad icon 526 for a selected period of time, such as fiveseconds. In one embodiment, the fully locked screen mode 525 can alsooccur due to a passage of a pre-selected amount of time. The partiallylocked screen mode 523 or the fully locked screen mode 525 can displaycontrol parameters for an extended period of time.

Turning to FIG. 5C, illustrated is an exemplary screen 530 of thedashboard 350 illustrating a display of discovered equipment in the HVACsystem 100. Generally, in prior art interfaces, a text list is used toinform a user/installer about found communicating devices in an HVACsystem. However, in FIG. 5C, icons or pictures of equipment 531-535 areused instead to help a user/installer understand what devices and/orequipment is connected to the HVAC system 100. In the exemplary screenof FIG. 5C, each of the discovered devices or equipment 531-535 has agraphical user interface (“GUI”) for employment by the installer,although other tabs of the dashboard 350 can also employ icons for foundor discovered equipment.

Turning now to FIG. 5D-1, illustrated is an exemplary embodiment of adashboard 350 having a lighting system 551 including a) a screen 555that needs a backlight to display information to b) a backlight 557 andc) a motion detector 559, wherein the backlight is turned on by themotion detector 559 upon a detection of motion within a selected range.The screen 555 can be an LCD screen.

Generally, the lighting system 551 allows a user to view indoorsettings, without having to touch a button on the dashboard 350, throughemployment of the sensor 559 and the backlight 557. With one embodimentof the system 551, a home owner can view indoor settings when passing bya dashboard 350, which activates the sensor 559 which then turns-on thebacklight. This allows a viewer to view settings of the dashboard,although indoor, from a distance, as determined by the sensor 559. Thiscan make for a convenient way for a user to view indoor settings whenthe backlight 557 is initially off, as it is switched on by the motiondetector 559. Furthermore, the system 551 can conserve energy and screen555 life when the backlight 557 is not on.

When the exemplary dashboard 350 is not being actively engaged by theuser (i.e., not being touched through a touch-screen interface and nomotion has been detected by the motion detector 559), the backlight 557is off. The screen 555 is then perceived as substantially dark 560, andno information can be read by a user, as is illustrated in FIG. 5D-2.

In the system 551, the motion detector 559 detects movement within aspecified distance of the dashboard 350 and commands the backlight 557to turn on, but otherwise does not allow the backlight 557 to turn on ifno motion is detected. For example, in FIG. 5D-3, the backlight is offbecause no movement, such as of a user 562, is detected within amovement detection zone 561, and the screen is dark 560.

However, once the movement is detected in the movement detection zone561 by the motion detector 559, such as a movement of the user 562, thenthe dashboard 350 turns on the backlight 557 so that information can beread from the screen 555 of the dashboard 350, such as illustrated inFIG. 5D-4. The user 562 may, therefore, be able to read the dashboard350 data on the screen 555 without having to walk up to the dashboardand touch the screen of the dashboard. This can also allow the user 562to press the dashboard 350 one less time, which can prolong atouch-screen life of the dashboard 350. When the user 562 walks closeenough to the motion detector 559 for the motion detector 559 to detectthe user's movement within the movement detection zone 561, then thebacklight 557 turns on and all buttons and tabs of the dashboard 350 areenabled. However, when the user 562 is out of range of the detectionrange 561, the system 551 again disables the backlight 557 and thevarious tabs, buttons, etc., and the screen is typically again dark 560,as illustrated in FIG. 5D-2.

Turning now to FIG. 5E, illustrated is an exemplary flow of screens 570of the dashboard 350. In the exemplary flow, an installer selects anitem of the screen 570 of an installer screen through an employment oftext 563, which itself can be a button to select the text. In otherflows, the text can be used in other screens of the dashboard 350.

In a further embodiment, the dashboard 350 has a screensaver thatactivates after a selected amount of inactivity from a user. In thisembodiment, the dashboard 350 allows a user to download an image for thedashboard 350 to display when it is idle. Thus, the dashboard 350 canbecome an equivalent of a digital photo-frame when its controls are notactive. In one embodiment, through pressing anywhere on a touch-screenof the dashboard 350 dismisses the screensaver image and re-displays thedashboard 350 controls.

Turning now to FIG. 6A, an exemplary humidity graphic 601 can be used toset humidify and de-humidify setpoints. In humidity screens 617, 619 ofthe humidity tab 360, a humidity status and RH humidity are bothdisplayed on a same screen of the humidity tab 360. Generally, a usermay not understand what XX % of humidity denotes on his or her dashboard350. Therefore, this embodiment of the screens 617, 619 both displaysthe RH and also interprets the RH.

In a further embodiment, below 36% the humidity graphic 601 reads“INDOOR RH XX %—DRY,” actual values can be between 35%-37%. Above 49%,the humidity graphic 601 reads “INDOOR RHXX %”—HUMID., actual value canbe between 48% and 50%. Between 36% and 49% RH, the display reads“INDOOR RH XX %—NORMAL” or “INDOOR RH XX % OK”, actual values can bebetween 35% and 50%.

An exemplary indoor humidity graphic shows a single bar 602 withrelative humidity (“RH”) being a calibrated item. A left side 603 of thebar 602 displays a current indoor RH level with the use of a triangle605, and a right side 604 uses a triangle 607 to show a current humidifyor dehumidify setpoint. Two up/down arrows 608 adjust a humiditysetpoint, and a switch button 613 transitions the humidity graphic 601to display either humidify comfort range setpoint or a de-humidifycomfort range setpoint. In other words, the humidity graphic 601 cantransition from the humidity screen 617 to a dehumidify screen 619.

Turning now to FIGS. 6B-1 through 6B-4, illustrated is an employment ofone a plurality of exemplary screens 631 of a humidity tab 360 of FIG.3D that is dependent upon equipment installed in the HVAC system 100 ofFIG. 1. In other words, if a given piece of equipment is not installedin the HVAC system 100, an indicia of that piece of equipment is notillustrated on the humidity screen of the humidity tab 360.

For example, the indoor humidity tab 360 can be dependent on humidifiersand cooling equipment. Without cooling, equipment, de-humidification isnot an option. Furthermore, the indoor settings tab 375 is dependent onheating and cooling equipment, and so is the programs tab 380.Therefore, the dashboard 350 removes modes, system setting options, andcontrol setpoints (humidity and temperature) based upon which pieces ofequipment to be discovered during an “installation and set-up process”are not actually discovered. Therefore, if a given piece ofhumidification or dehumidification equipment is not present, it may notbe displayed in the screens 631.

For example, FIG. 6B-1 shows an indoor humidity screen 633 a, an indoorsetting screen 633 b, a programs summary screen 633 c and a programsinput screen 633 d with all options and services available. FIG. 6B-2shows equivalent screens, here designated 635 a-635 d, based on onlyheating equipment and a humidifier being installed. FIG. 6B-3 showsequivalent screens, here designated 637 a-637 d, based on only coolingequipment being installed, without a humidifier. Finally, FIG. 6B-4shows the indoor humidity screen, here designated 639, for which onlyheating equipment is installed, without a humidifier. As is illustrated,equipment that is not available is not illustrated. In furtherembodiments, interface screens correlating to indoor settings tab 375and programs tab 380 do not display indicia of devices not installed inthe HVAC system 100, either.

In a further embodiment, the humidity tab 360 allows users to have andconfigure different humidity levels during different periods of a day.These periods could be a wake, leave, return and sleep period, forexample. For an exemplary instance of use, a user can have 40% humiditylevel in the morning, and 45% humidity level at night in the same day.Additionally, users can have different humidity levels for differentdays or group of days. Some parts of the country can have changes in itshumidity level throughout the day, so therefore users who reside inthese areas can maintain their comfort inside of their homes by usingthis feature.

Turning now to FIGS. 7Ai through 7Aiv and FIGS. 7Bi through 7Biv,illustrated are an exemplary flows of various transitions of a helpscreen having a help tab 370 of the dashboard 350 that are dependentupon or otherwise determined at least in part by a screen displayedbefore the help tab 370 is activated.

Generally, a purpose of interactive help for the HVAC system 100 is fora user or installer to navigate throughout the dashboard 350 without theuser or installer having to go find a manual and look up a particularfunction or dashboard 350 screen shot. Discussed below are an exemplaryflow 710 and a flow 750, both to help accomplish this goal ofnavigation.

FIGS. 7Ai through 7Aiv, collectively referred to as FIG. 7A correspondsto an example flow 710. FIGS. 7Bi though 7Biv, collectively referred toas FIG. 7B, corresponds to an example flow 750, Both the flows 710, 750allow a user to get help on current dashboard screens without changinghis or her current dashboard 350 settings. A help interface cantherefore be located in the dashboard 350, and the user/installer doesnot necessarily have to find or use an independent manual.

An approach of the exemplary flow 710 of FIG. 7A is directed towardsdependent settings for help screen sequences. The flow 710 illustrateshelp screens that progress in a predetermined sequence depending on thescreen shown before the help tab 370 is pressed. Generally, help issupposed to teach a user and not confuse them more; therefore, help inthe flow 710 does not display information about possible settings thatwere not displayed on the screen before the help tab was pressed.

For example, the exemplary flow 710 displays 3 different screens 711(FIG. 7Ai), 712 (FIG. 7Aii), 713 (FIG. 7Aiii) that could be displayed toa user before a help tab 370 is pressed. After the help tab 370 ispressed, the screen transitions as follows: the screen 711 transitionsto a screen 714 (FIG. 7Ai); the screen 712 transitions to a screen 715(FIG. 7Aii); and the screen 713 transitions to a screen 716 (FIG.7Aiii). Thus, each screen 711, 712, 713 progresses to its correspondingparticular screen 714, 715, 716, respectively, that contains informationspecific to the screen transitioned from. The help screens 714, 715, 716each contain a text box and arrows that give information about aparticular area of the screen that was present before the help wasinvoked.

Pressing anywhere on a help screen 714, 715, 716 transitions the helpscreen to a screen 717 (FIG. 7Aiv). This particular screen 717 is usedfor all the screens 711, 712, 713, because the screen 717 row C providesinformation about a common item for all the screens 711, 712, 713.

Touching the screen 717 transitions to a screen 718, (FIG. 7Aiv). Thisis yet another screen that displays common information for all thescreens 711, 712, 713. A screen 718 (FIG. 7Aiv) is the last screen inthe help sequence 710. Pressing the screen 717 of the dashboard 350transitions back to the screen displayed before the help tab 370 waspressed, via a step 720.

Turning now in a further embodiment to FIGS. 7Bi through 7Biv,collectively referred to as FIG. 7B, help screens of the help tab 370allows a user to adjust settings on a help screen without saving changesto the settings to the HVAC system 100. Generally, once the user exits ahelp screen, all the settings or screen changes return to their previousstate before the help tab 370 was pressed, which allows a user toexperiment with settings of a screen without saving them to the HVACsystem 100.

An exemplary screen 751 of the flow 750 of FIG. 7B is the screendisplayed on the dashboard before a help tab 370 press. A screen 752 isthe screen displayed immediately after a help tab 370 is pressed. Adifference between screen 751 and 752 of flow 750 is a text box.

The text box on screen 752 gives a brief explanation about a currentscreen, and tells the user to touch an area of interest to get moreinformation. Assuming that a user wants to know more about “currenttemp” and pressed in this area, for example, then the screen progressesto a screen 753 (FIG. 7B ii) with a new text box listing informationabout “current temp.”

A screen 754 is shown after the “fan setting” area is touched. However,this area of the screen contains a select button. In one embodiment,pressing the select button changes the screen to a screen 755 (FIG. 7Biii) with a new text box listing information about the new setting. Thetransition from the screen 754 to the screen 755 not only shows a newtext box, but it also changes the highlighted setting from “on” to“circulate.” In one embodiment, the screen 755 transitions to a screen756 (FIG. 7Biii) if the system setting area is pressed. In oneembodiment the screen 756 transitions to a screen 757 (FIG. 7B iv) ifthe select button is pressed. However, the screen 757 transitions backto the screen 751 of FIG. 7Bi, the screen displayed on the dashboardbefore the help tab 370 press.

Turning now to FIGS. 8A-8D, illustrated are various views of a screen831 dependent upon equipment being found in the HVAC system 100 of FIG.1, as discussed regarding the screens 631 of FIGS. 6B-1 through 6B-4,above. In FIG. 8A-8C, a screen 83*a is an indoor humidity screen, ascreen 83*b is an indoor settings screen, a screen 83*c is a programsummary screen, and a screen 83*d is a program input screen.

Regarding FIG. 8A, screens 833 a-833 d show the screen 831 all optionsand services available. In FIG. 8B, screens 835 a-835 d illustrate thescreen 831 for the case in which no cooling equipment is installed. InFIG. 8C, screens 837 a-837 d illustrate the screen 831 for the case inwhich no heating equipment is installed. And FIG. 8D illustrates anindoor humidity screen 839 reflecting the case in which heatingequipment is installed but no humidifier is installed. As isillustrated, equipment that is not available is not shown in the screen831.

Turning to FIG. 9A, illustrated is an exemplary programs screen 910 ofthe programs tab 380 that displays all program time periods andprogrammed temperature setpoints for the programs tab 380. In thisembodiment, all program schedule setpoints 912, 914, 916, 918 aredisplayed on one programs screen 910. All time periods for a programschedule are displayed as well. In the illustrated embodiment of thescreen 910 of the programs tab 380, time is listed first, then heattemperature, cool temperature, and fan settings are last. The screen 910can be a 4×4 matrix with only one setpoint area/button being selectableat a time. In one embodiment, once a setpoint area is touched, the boxturns an inverse of its current color. In the illustrated embodiment,up/down arrows 921 are used to adjust each setpoint/setting.

Turning now to FIGS. 9B-1 and 9B-2, illustrated is an exemplary flow 930of programs screens. The screens of the programs tab 380 include buttons933 that turn an inverse color as a selection and touch reaction. Forexample, FIG. 9B-1 illustrates a programs screen 932 with a particularbutton 933 not being touched. A programs screen 934 illustrates the casethat a button 935 being touched, and turning an inverse color. In FIG.9B-2, a screen 936 illustrates the button 935 staying an inverse color,and an arrow button 937 turning an inverse color. A screen 938illustrates that the button 935 stays the inverse color, but an arrowbutton 939 reverts to its previous color.

In one embodiment, any touched button of the buttons 933 of the flow 930turns an inverse color while being touched. If the button could beadjusted to another value, then the button/selection box remainsinverted as to color even when the user is no longer touching thebutton, such as the button 935. However, if the button is an up/downarrow, for example the button 937, then the button only turns inversewhile the user is touching that button. In other words, when the userreleases the button, such as an up/down button, then the button returnsto its normal color/state, as illustrated by the button 939. In otherembodiments, the button color inverse can occur in other tabs, such asthe home tab, the humidity tab, and so on.

Turning now to FIG. 9C, illustrated is a program schedule in a programsscreen 940 of the programs tab 380 partitioned into a plurality of timezones wherein, upon a button corresponding to a time zone 941 beingpressed for a set period of time: a) a temperature setpoint for thattime period is deactivated, b) a display of the deactivated setpoints ofthe deactivated time period now appears dim relative to a display of thetime period's setpoints before deactivation; and c) the deactivated timeperiod's setpoints 943 appear dimmer relative to an active time period'ssetpoints.

In the illustrated embodiment of FIG. 9C, if one of the time zones 941is pressed and held for approximately two seconds, then the setpointsfor that time period 943 is deactivated. In one embodiment, the timeperiod 943 is then controlled by the previous time period's setpoints.

Turning now to FIG. 9D-1, illustrated is an interface 950 for setting asystem time for an HVAC system 100, such as through a programs screen ofthe programs tab 380. Setting a system time involves 6 boxes. Each boxcontains a particular aspect of time and date. Only one box can bechanged by a user at a time. FIG. 9D-1 generally discloses an analogclock interface 950 with date and time selection boxes. The date andtime selection boxes are as follows: hour box 961, minute box 962, AM/PMbox 963, month box 964, day box 965 and year box 966.

Generally, in the clock interface 950, the hands 958, 959 of the clockinterface 950 are moved by touching them and dragging them to a desiredposition, either through a touch screen or with a device such as atrackball. The hour hand 958 and the minute hand 959 are linked to theircorresponding boxes 961, 962, and the boxes 961, 962 change if theircorresponding hands are adjusted. For example, if the hour hand 958 ischanged from “12” to “6,” then the hour box 961 changes from “12” to“6.” The up and down arrows 960 can also be used to adjust eachinterface box. Typically, in the interface 950, at least one value of atleast one interface box is changed as a user drags at least one clockhand of the analog clock. Generally, in the interface 950, at least onevalue of at least one number itself is used as an input to a box, andthe analog clock face maps to the changed value.

Turning now to the clock interface 965 of FIG. 9D-2, the clock facenumbers themselves are used as buttons, a selection of any of whichdefine where clock hands 973, 974 point and values in boxes 971, 972.Either the hour 971 or minute 972 box is selected, and then the desirednumber on the clock face is pressed, upon which both the hour hand 973or minute hand 974 jump to that setting, and boxes 971, 972 fill in forthat value. For example, if the hour box 971 is selected and the currentsetting is “5,” and then the clock face number “10” is pressed, thenboth the hour hand 973 jumps to “10” and the hour box 971 adjusts to“10.” The up and down arrows 960 can be used to adjust each box.

Turning now to FIG. 9E, illustrated is an embodiment of a programsscreen of the programs tab 380 and a reset interface 975 for the same.Generally, the reset interface 975 of FIG. 9E can help a user reset topredetermined default setting, such as a factory setting 976 or anothercustom setting 977, when a user inadvertently changes one or moresettings, or otherwise wishes to go back to these settings. Without thereset interface 975, a user might have to spend a considerable amount oftime reviewing an owner manual and/or scrolling through a plurality ofmenus to locate the erroneous or unwanted settings, and may not knowwhat the reset settings even are. As is illustrated, there are differentselections for settings, temperature, clock, daylight savings time,display and backlight.

All buttons in FIG. 9E that are in grey represent an exemplary set ofemployed reset values or parameters as currently selected in theillustrated exemplary reset interface 975 upon an exit from the resetinterface 975. These reset selections are employed by the HVAC system100. These reset values over-ride whatever is currently being employedin the HVAC system 100. However, any reset value may be changed, asdescribed below.

Generally, the reset interface 975 can select from a default value amongthe following values: a user can reset the dashboard 350 to the factorysetting 976 or to another value, such as the custom value 977 programmedby an installer. For example, if programming or operating becomesconfusing or other issues occur, the customer can reset the values tothese prior settings. The reset screen 975 provides a reset unit ofmeasurement in either the British unit (Fahrenheit) 978 or a S.I. 979unit (Celsius).

The user may select a reset to a 12 hour 980 or 24 hour 981 clock. Ifusers prefer the 24 hour clock rather than the “12” hour clock, he orshe can do so via this change. The user can also adjust or correct thetime, for any reason, including daylight savings times 982, 983.

A user may also set the default language: the consumer or dealer canreset to an exemplary preferred language 984-987 or change it, ifneeded. The customer can reset the backlight brightness, such asbacklighting for high 991, medium 990, low 989, or off 988.

Generally, when the installer first installs the equipment, theinstaller will be able to set all parameters outlined above as part ofthe initial set up and commissioning of the dashboard and system. Aninstaller or user can save the settings through a save button 992, orexit with an exit button 993. When the settings are saved, thisover-rides any other programming or configuration in the HVAC system100.

Turning now to FIG. 9F, illustrated is an exemplary programs screen thatfurther includes a display of a plurality of pre-populated programschedule settings. The pre-populated program settings selection choicesrange from a maximum comfort 994 to a maximum energy savings 998 of therange. The settings employ a slider 992 between the maximum comfortsetting 994 to the maximum energy savings 998 of the selection basedupon a selector 999. Furthermore, based on a selection of a user, aprogram schedule of the programs tab 380 automatically populatestemperature and humidity settings for each program scheduled event, toachieve a desired selection. This can occur in the programmed setpointsfor both temperature and humidity, and further embodiments can includethe activation or deactivation of pieces of various environmentalequipment, such as heaters, coolers, fan blowers, humidifiers,dehumidifiers, etc.

Turning now to FIGS. 9Fi and 9Fii, illustrated are exemplary flows ofprogramming screens that can be used with this embodiment. In flow 1000of FIG. 9Fi, for a dashboard 350 that is running a program schedule, andflow 1006 of FIG. 9Fii, for an embodiment of the dashboard 350 that isnot running a program schedule, instead of a user directly entering thenecessary values, the user instead sets the slider 992 of FIG. 9F, andthe values are entered into these screens by the slider 992. The flow1000 has a screen 1001, 1002, 1003, 1004, and 1005. The flow 1006 has ascreen 1007, 1008 and 1009.

In one embodiment, if a change of operating parameters is made in theprograms screen of the programs tab 380 while a current program isrunning which employs previously entered parameters, a hold time can beprogrammed within the programs tab 380, wherein the hold time is enteredas exactly what time the previous parameters are to stop taking effect.

In a further embodiment, the dashboard 350 has to setparameters/settings for all devices in the HVAC system 100. There are afew parameters, such as for a blower, that have large ranges that can bevery time consuming to set with up and down arrows. Therefore, a coarsescroll bar and a fine scroll bar can be used to adjust such settings(not illustrated). First, the coarse bar is adjusted to get close to thedesired range, and then the fine bar is adjusted to get to the exact andprecise settings. This can be done by a dashboard 350 that is orincludes a touch-screen.

Turning now to FIG. 10A, illustrated is an exemplary flow 1010 employingthe home screen 450. In a first screen 1015, a particular icon 1017,such as the “Lennox”™ icon, is placed on the home screen 450 to enablean access of an installer screen. In FIG. 10A, in order to access aninstaller screen from the home screen 450, an installer is to both a)press and hold the icon 1017 with a finger for at least five seconds;and then b) drag the finger across the interface, as illustrated inscreen 1020. The button hold and drag is to be performed without liftinga finger for the installer screens to be accessible from the homescreen. Otherwise, the screen 1015 generates a warning screen 1025.

In a further embodiment, the dashboard 350, such as in the home screen450, has a single alert icon 1018 that gives a user an indication thatthere is at least one alert present. In one embodiment, the alert icon1018 is one of three colors: a) a first color to indicate that the HVACsystem 100 is currently running in an energy efficient mode; b) a secondcolor to indicate that a filter of the HVAC system 100 needs to bereplaced; and c) a third color to indicate that a piece of equipment isno longer working.

Pressing the alert icon 1018 directly navigates to a display page on thedashboard 350, such as found in the alerts tab 365, giving a user: a)more information about at the least one alert; b) the ability to clearthe at least one alert; or c) to set a reminder time for a later datefor the at least one alert.

Furthermore, a color of the alert icon 1018 can be changed to signal adifferent level of severity alert that is present. For example, a“green” alert icon 1018 could signal that the HVAC system 100 iscurrently running in an energy efficient mode. A “yellow” alert icon1018 could signal that a filter needs to be replaced. A “red” alert icon1018 could signal that a critical piece of equipment is no longerworking.

Turning to FIG. 10B, illustrated is an exemplary flow 1030 thattransitions from a home screen 450 to a tabbed interface 1040. In FIG.10B, if a user touches anywhere that is not a button, such as an area1035, a tabbed interface 1040 arises, each of the interfaces (humidityscreen, help screen, etc.) accessible through its corresponding tab355-390.

Generally, the flow 1030 gives a user a straightforward interface thatcan easily get indoor settings and system information. With a simplescreen press, such as in an area 1035, a user can get the tabbedinterface 1040, thereby allowing a change of a system or mode setting,or to otherwise get more detailed information about aspects of the HVACsystem 100.

The home screen with the tabbed interface 1040 of FIG. 10B also allowsthe user to change a current temperature setpoint without necessarilyhaving to deal with much further information. Therefore, all a userneeds to do is press anywhere inside an “indoor conditions” area (thatis not a button) and the home screen 450 transitions to the tabbedinterface 1040 where all indoor settings can be changed in the indoorsettings tab 375 and more detailed information can be obtained.

In a further embodiment, the home screen 450 can be a “default screen”for the dashboard 350 and gives the user general information aboutindoor conditions. In a still further embodiment, an icon of the homescreen 450 is correlated to at least one HVAC system mode or fan mode.In this embodiment, for example, a fan icon can be used to represent atouch area for a user to press if the user wants to change a fanschedule in the dashboard 350. Similarly, in some embodiments, a “flameand flake” icon can be used to represent a system mode button that auser may wish to change.

In a yet further embodiment of the home screen 450, at least oneattribute of a presentation of the home screen is selectable by a user.For example, differing presentations can be mode of comfort backgrounds.One example could be a black and white screen for a background of thehome screen 450; another example could be use of a larger font size onthe home screen 450, etc.

Turning now to FIGS. 11A-1 and 11A-2, illustrated are two exemplaryembodiments of an installer dashboard 1030 to be used in conjugationwith the installer flow 401 and its various tabs and screens. Theinstaller dashboard 1030 can be considered a subset of the dashboard350, and is contained within the dashboard 350, although both thedashboard 350 and the installer dashboard 1030 are accessible remotely.

Pressing the installation setup tab 402 can change the active tab to aninstallation setup screen of the installer screen flow 401. In someembodiments, when accessing the installer screens, the dashboard 350defaults to showing the installation setup tab 402 as active.

Pressing the tests tab 404 can change the active tab to an installertests screen of the installer screen flow 401. Pressing the installerhelp tab 414 provides “context sensitive” help that presents dialogboxes relating to current screen functions regarding installation of theinstaller screen flow 401. Pressing the alerts tab 408 changes theactive tab to the (installer) alerts screen of the installer screen flow401. The diagnostic tab 406 is only active once the HVAC system 100 hasbeen configured. Pressing the diagnostic tab 406 changes the active tabto the diagnostics screen of the installer screen flow 401. Pressing theexit tab 1107 advances the installer to the home screen 450—leaving theinstaller screens. If available, pressing the start tab 1105 allows theHVAC system 100 to begin operating.

Turning now to FIG. 11B, illustrated is an installation and setup screen1120 that displays minimum 1127, maximum 1129, current 1130 and default1131 values on one screen for a device setting in an installation screenof the installer screen flow 401 for a particular device in the HVACnetwork 200 of the HVAC system 100. In one embodiment, the device to beinstalled sends a message to the dashboard 350 with the minimum, maximumand factory default values. In a further embodiment, the device to beinstalled can send increment values. The setup screen 1120 then displaysall of this information to the installer. This gives the installerbetter information to set device parameters.

Turning now to FIG. 11C, illustrated is an exemplary installer screen1140 illustrating an underlining 1141 of factory default settings fordevice parameters of the HVAC system 100. Generally, when multiplesettings are displayed on one screen, under-lining 1141 one of thelistings allows an installer to know what the factory default settingis, even when a separate entry 1142 is an option that is currentlyinstalled.

Turning now to FIGS. 11D-1 and 11D-2, illustrated is a flow 1155 whereina device within the HVAC system 100 to be diagnosed in the installerscreen 1140 is moved as text by a finger movement from a left part 1191of the installer screen 1140 to a right part 1196 of the installerscreen 1140.

In some embodiments, this approach does not need a select button or aremove button. Instead, an installer touches a desired item/device, suchas item 1194 (FIG. 11D-1), and drags the text or icon to the right part1196, creating an absence 1195, and then releases (FIG. 11D-2). Once thedevice is on the right part 1196, it is no longer on the left part 1191,and a start button 1197 appears, letting the installer know that theinstaller may proceed with diagnostics. To remove the selected item,simply drag it back to a list on the left part 1191.

Turning now to FIG. 12, illustrated is an exemplary method 1200 foroperating and/or providing a visual interface for an HVAC network of anHVAC system, such as the HVAC network 200.

In a step 1201, a weather tab that invokes a weather screen is provided.In a step 1220, an indoor humidity tab that invokes an alert screen isprovided, wherein invoking the indoor humidity tab advances to ahumidity screen which displays at least a current indoor humidity. Instep 1230, an alerts tab that invokes an alerts screen is provided. In astep 1240, a help tab that invokes a help screen is provided, whereininvoking the help tab advances to a help screen that provides contextsensitive help that presents at least one dialog box related to afunction of a current screen. In a step 1250, an indoor settings tabinvokes an indoor setting screen which includes a current indoortemperature. In a step 1260, a programs tab that invokes a programsscreen is provided which can program at least one of a) time b)temperature setpoints and c) heating/cooling setpoints. In a step 1270,a home tab provides a summary of indoor conditions. In a step 1280, atleast one of the screens from the above steps is invoked.

In a further embodiment of the method 1200, step 1270 further provideswherein the home tab can advance to an installer dashboard that can beaccessed only by an entry of a key, wherein the key is entered by aninstaller. In a further embodiment of method 1200, step 1260 furtherprovides that, upon a time zone being pressed for a set period of timein the programs screen: a) a temperature setpoint for that time periodis deactivated; b) a display of the deactivated setpoints of thedeactivated time period appear dim relative to a display of the timeperiod setpoints before deactivation; and c) the deactivated timeperiod's setpoints appear dimmer relative to an active time periodssetpoints. Step 1260 also still further provides a display of aplurality of pre-populated program schedule settings.

The method 1200 yet further includes a further embodiment of step 1240,wherein the help screen further displays settings dependent upon ascreen displayed before the help screen is invoked. A still furtherembodiment of the method 1220 includes a further embodiment of step1220, wherein the humidity screen allows users to program differenthumidity levels for different periods of a day. A yet still furtherembodiment of step 1250, wherein for a given piece of equipment to beoffered to a user, a corresponding piece of equipment is installed inthe HVAC dashboard.

Turning now to FIGS. 13A and 13B, illustrated is an exemplary flowdiagram 1300 illustrating a subnet controller controlling a userinterface display, which in some embodiments can be used in conjunctionwith or as a further embodiment of the method 1200.

Message(s) 1: subnet controller 1310 tells UI 1320 to display a specificscreen and instructs it how to fill the data fields (TITLE, FIELDx,VALUEx, UNITx field as well as instructions on Buttons—how many thereare, what their caption is). For example, to fill FIELD2 use UI stringnumbers 1234, to fill VALUE2 field, look at message with ID 12093 andstarting bit 16 (3^(rd) byte of the message) take 16 bits out andinterpret them as unsigned int (16 bit), to fill UNIT2 field, use unitsof F/C (indicates temperature, for example.)

Message(s) 2: subnet controller 1310 tells device(s) 1330 to startoperating—performing whatever test they are to perform.

Message(s) 3: device(s) 1330 broadcast their status and/or diagnosticmessages and the UI 1320 interprets and displays the data, as it wastaught by message(s) 1.

Message(s) 4: UI 1320 lets the subnet controller 1310 know which buttonwas pressed, the subnet controller 1310 interprets this as either a SKIPTEST (go to the next one, or if on the last one, go to the resultspage), TEST PASSED or TEST FAILED, as appropriate. After this, the wholeprocess repeats for all tests. An exemplary user interface screen shotafter completion of a test can be seen in FIG. 13B.

Those skilled in the art to which this application relates willappreciate that other and further additions, deletions, substitutionsand modifications may be made to the described embodiments.

1. An HVAC graphical interface dashboard, comprising: a weather tab,wherein invoking the weather tab advances to a weather screen; an indoorhumidity tab, wherein invoking the indoor humidity tab advances to ahumidity screen which displays at least a current indoor humidity; analerts tab, wherein invoking the alerts tab advances to an alertsscreen; a help tab, wherein invoking the help tab advances to a helpscreen that provides context sensitive help that presents at least onedialog box related to a function of a current screen; an indoor settingstab, wherein invoking the indoor settings tab advances to an indoorsettings screen which includes a current indoor temperature; a programstab, wherein invoking the programs tab advances to a programs screenwhich can program at least one of: a) a time; b) temperature setpoints;c) heating/cooling setpoints; and a home tab, wherein invoking the hometab advances to a home screen which provides a summary of indoorconditions; and wherein a subnet controller informs said dashboard todisplay a specific screen and instructs it how to fill in data.
 2. Thedashboard of claim 1, wherein said instruction include a selection oftwo or more data fields.
 3. The dashboard of claim 1, wherein saidinstruction are directed toward dashboard buttons per screen includingat least one of: a) how many there are; and b) what a caption is pereach button.
 4. The dashboard of claim 1, further comprising said subnetcontroller is coupled to a device and instructs said device to operate.5. The dashboard of claim 1, wherein said dashboard displays informationgenerated by said device according to said instructions of said subnetcontroller.
 6. The dashboard of claim 5, wherein said dashboard conveysto said subnet controller which button was pressed upon a pressing ofsaid button.
 7. A method for operating an HVAC interface having aplurality of tabs, comprising: providing a weather tab, wherein invokingthe weather tab advances to a weather screen; providing an indoorhumidity tab, wherein invoking the indoor humidity tab advances to ahumidity screen which displays at least a current indoor humidity;providing an alerts tab, wherein invoking the alerts tab advances to analerts screen; providing a help tab, wherein invoking the help tabadvances to a help screen that provides context sensitive help thatpresents at least one dialog box related to a function of a currentscreen; providing an indoor settings tab, wherein invoking the indoorsettings tab advances to an indoor settings screen which includes acurrent indoor temperature; providing a programs tab, wherein invokingthe programs tab advances to a programs screen which can program atleast one of: a) time; b) temperature setpoints; c) heating/coolingsetpoints; providing a home tab, wherein invoking the home tab advancesto a home screen which provides a summary of indoor conditions; andinforming said dashboard by a subnet controller to display a specificscreen and instructs it how to fill in data.
 8. The method of claim 7,wherein said instruction include a selection of two or more data fields.9. The method of claim 7, wherein said instruction are directed towarddashboard buttons per screen including at least one of: a) how manythere are; and b) what a caption is per each button.
 10. The method ofclaim 7, further comprising said subnet controller is coupled to adevice and instructs said device to operate.
 11. The method of claim 7,wherein said dashboard displays information generated by said deviceaccording to said instructions of said subnet controller.
 12. The methodof claim 7, wherein said dashboard conveys to said subnet controllerupon a pressing of a button.
 13. The method of claim 12, wherein saidsubnet controller interprets said button press as a skip test commandfrom a user.
 14. The method of claim 7, wherein said subnet controllerinterprets said button press as one of a a) test passed; and b) testfailed indication from a user.
 15. An HVAC system including a graphicalinterface dashboard and at least one coupled device, comprising: thedashboard, including: a weather tab, wherein invoking the weather tabadvances to a weather screen; an indoor humidity tab, wherein invokingthe indoor humidity tab advances to a humidity screen which displays atleast a current indoor humidity; an alerts tab, wherein invoking thealerts tab advances to an alerts screen; a help tab, wherein invokingthe help tab advances to a help screen that provides context sensitivehelp that presents at least one dialog box related to a function of acurrent screen; an indoor settings tab, wherein invoking the indoorsettings tab advances a user to an indoor settings screen which includesa current indoor temperature; a programs tab, wherein pressing theprograms tab invokes a programs screen which can program at least oneof: i) a time; ii) temperature setpoints; iii) heating/coolingsetpoints; and a home tab, wherein invoking the home tab advances a userto a home screen which provides a summary of indoor conditions; and theat least one coupled device selected from the group including: a) an airhandler; b) a furnace; c) an evaporator coil; d) a condenser coil; ande) a compressor; wherein the at least one coupled device is viewablefrom at least one of the tabs, and a subnet controller informs saiddashboard to display a specific screen and instructs it how to fill indata.
 16. The dashboard of claim 1, wherein said instruction include aselection of two or more data fields.
 17. The dashboard of claim 1,wherein said instruction are directed toward dashboard buttons perscreen including at least one of: a) how many there are; and b) what acaption is per each button.
 18. The dashboard of claim 1, furthercomprising said subnet controller is coupled to a device and instructssaid device to operate.
 19. The dashboard of claim 1, wherein saiddashboard displays information generated by said device according tosaid instructions of said subnet controller.
 20. The dashboard of claim1, wherein the indoor humidity tab can further be used to set currentindoor humidity setpoints.